…data

Found while double-checking the state of main after #44/#45 merged.
verisim/seed/repos.a2ml was NOT valid TOML — tomllib.load() errored
before this fix. Four bugs, all pre-existing (not introduced by #44/#45):

- [repo..git-private-farm] and [repo..github]: repo names starting with
  a literal dot produce an empty key segment between the two dots
  (repo + "" + git-private-farm) — a hard TOML parse error. Quoted:
  [repo.".git-private-farm"] / [repo.".github"].
- [repo.hyperpolymath.github.io] and [repo.EchoTypes.jl]: these parse
  (dots are valid bare-key separators) but as 3-level nested tables
  (repo.hyperpolymath.github.io, repo.EchoTypes.jl) instead of the
  clearly-intended single table keyed by the literal name — silently
  wrong structure, not a parse error. Every sibling .jl-suffixed entry
  in the file already quotes correctly (e.g. [repo."Axiom.jl"]); these
  two just missed it. Quoted to match.
- [repo.verisimdb-data] was declared TWICE (line 374, hand-curated:
  clade=db, completion=50; line 2650, from the 2026-06-25 heuristic
  backfill: clade=rm, completion=0) — TOML forbids redeclaring a table,
  so this alone made the file unparseable regardless of the key-quoting
  bugs above. Kept the original (line 374); removed the backfill
  duplicate. worker/data/repos.json's single verisimdb-data entry had
  the same problem in miniature (it held the backfill's clade=rm
  values) — reconciled to match the surviving canonical entry.

Verified: `python3 -c "import tomllib; tomllib.load(...)"` now succeeds
(319 repo entries) and worker/data/{repos,index}.json still validate as
JSON (JSON keys are always quoted, so it can't have the same key-parsing
bug, but repos.json's verisimdb-data value was wrong regardless).